(Item 8303) Allow signaling information definition at DLUR ----------------------------------------------------------- DLUR signaling information is currently defined via DLCADDR at the DLUS. While some users prefer centralized (at DLUS) signaling information definition, there are others who prefer distributed (at DLUR) definition. The DLUS does not require DLCADDR to be defined, so some or all of the information currently defined via DLCADDR at the DLUS should be allowed to be optionally sysdefed at the DLUR instead. * DLUR-initiated SSCP-PU activation --------------------------------- It appears that the DLUR already has the signaling information it needs when it builds REQACTPU. If this is true, it shouldn't be necessary to: - define the same signaling information at the DLUS - send the same signaling information with ACTPU DLUR can send the signaling information with REQACTPU; the DLUS uses it for: - network management - CSX user exit for connection verification and accounting - internal PU correlation * DLUS-initiated SSCP-PU activation --------------------------------- If the DLUS has only partial signaling information defined, it does not affect: - network management - CSX user exit for connection verification and accounting - PU correlation Some, if not all, of the signaling information defined at the DLUS via DLCADDR could be optionally defined at the DLUR. The proposed solution is to update the DLUR architecture reference as follows: Signaling Information - This parameter will identify the DLUR-to-PU connectivity. This information must be coordinated between the DLUR and DLUS nodes: 1) it can be defined completely at the DLUR - in this case some or all of the information can optionally be sent to the DLUS to be used for network management, input into the Configuration Services XID exit for connection verification and accounting, and PU correlation 2) it can be defined completely at the DLUS - in this case all of the information will be sent to the DLUR on the ACTPU 3) it can be defined partially at the DLUS and partially at the DLUR - in this case the DLUR can optionally send the DLUR-defined signaling information (for the reasons described above) while the DLUS-defined signaling information will be sent on the ACTPU - if upon receipt of the ACTPU, the DLUR determines it has incomplete signaling information, it can optionally proceed with the activation (using defaults) or it can fail the activation - if upon receipt of the ACTPU, the DLUR determines it has the same signaling information subfield from both the DLUR and DLUS, but the subfields have different values, it will use the values provided by the initiator of the activation